home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
The World of Computer Software.iso
/
mvssrc.zip
/
$$DOC
next >
Wrap
Text File
|
1992-04-13
|
3KB
|
63 lines
This is a sample TCP MVS server that incorporates both the socket
library and MTF subtasks. IBM'S TCP/IP version 2.1 is required.
because this server utilizes MTF, PTF UN13465 (APAR PL83602) is also
required.
I apologize for not providing a better installation; However, I am no
longer permitted to work on it and so must provide it as-is. I would be
happy to to try to answer any questions anyone would have about how to
set it up, as time permits. NO ONE else at the University of Delaware
is involved in this software, and it is not sanctioned by my department
so please don't bug other UD folks about it. Hopefully someone else
will pick up support of this software and finish it. If anyone's
interested, I can supply some ideas on what still needs to be done. Just
send mail to SHAWN.HART@MVS.UDEL.EDU.
This server supports the required record types as documented in the
original gopher protocol document. (This document can be retrieved from
ANONYMOUS FTP at BOOMBOX.MICRO.UMN.EDU.) Note it does not support
recent changes to the index server records.
BERORE YOU COMPILE:
Before you compile this program, make sure you look at the defines in
the TCPH member; that's where the default main index is defined.
When For the brief period of time we ran this server, (about a month) I
ran it as a started procedure. If you do this, be sure the userid you
choose to run it under only has authority to access the gopher datasets
you specified...
I was a little concerned about how much CPU this was using; we seemed to
average 100 -200 connections a day, with the CPU use in the 12-14 second
range (per day) on our 300E. The largest number of connections I saw
was 1,405 in a single day, with the CPU use around 60 CPU seconds. We
speculate that the majority of this time is spent in creating the TCP
connection. CSTORE use seems to be reasonable, around 200K when
inactive, about 500K active, when 8 subtasks are defined.
THINGS I WANTED TO DO
1. Make the link file keywords match those of the UNIX server
2. Support more of the optional data types in the server (Easy!)
3. add indexing support, either by porting the WAIS server libs
to MVS & writing an engine, or developing a VSAM interface (?)
MEMBERS IN THIS PDS:
The following members are included in this PDS. (If you are not
using the IEBCOPY version of this distribution, then place each
file in a PDS member)
$$DOC - This member 1 16 16 0 SYS0008
$$MAKE - a CLIST that punches JCL & submits a compile job 5 96 211 0 SYS0008
COMPILE - JCL to compile the main task & MTF subtask
EBDASC - ASCII to EBCDIC translate table & function 8 79 79 0 SYS0008
GOPHER - main MTF task for gopher 0 186 172 0 SYS0008
GPHPTSK - MTF subtask for gopher connections 9 496 30 0 SYS0008
MTFERROR - Error routine hack for MTF environment 9 151 151 0 SYS0008
LINKSAMP - Sample link file
TCPH - Header stuff for gopher main & subtasks 2 65 9 0 SYS0008
TCPINCL - include files for gopher main * subtasks 4 25 13 0 SYS0008
TCPRUN - sample job to run the gopher server 3 13 12 0 SYS0008